named [FAILED] - zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. - bind error solution
Centos when copying old files and restarting it seems load everything fine and then says [FAILED] with no log or other message.
service restart named
named [FAILED]
Check more thoroughly you may have missed the error if you have lots of zones!
service named restart|grep error
zone 1.168.192.in-addr.arpa/IN: not loaded due to errors.
zone 2.168.192.in-addr.arpa/IN: not loaded due to errors.
zone 3.168.192.in-addr.arpa/IN: not loaded due to errors.
Check the zone file you probably made a mistake that was accepted in an older version of bind/named:
$TTL 60 ; 172800 seconds
$ORIGIN 3.168.192.IN-ADDR.ARPA.
@ IN SOA ns1.rtt.com. ns2.rtt.com. (
2003080854 ; serial number
3h ; refresh
15m ; update retry
3w ; expiry
3h ; nx = nxdomain ttl
)
IN NS ns1.rtt.com
IN NS ns2.rtt.com
2 IN PTR testdns.com.
3 IN PTR dubmail-smart-www.testdns.com.
4 IN PTR path-mail-vlan20.testdns.com.
17 IN PTR testdns.com.
18 IN PTR tehka.testdns.com.
19 IN PTR khyra.testdns.com.
20 IN PTR skulda.testdns.com.
21 IN PTR thehip.testdns.com.
22 IN PTR ccipe.testdns.com.
Notice above how the IN NS does NOT have a period at the end of the TLD or .com
This is a mistake and not allowed and not tolerated in modern versions of bind but clearly in previous ones it was fine and working!
So just add the dots at the end like below and it will be good.
IN NS ns1.rtt.com.
IN NS ns2.rtt.com.
The above is just a real life example and there was no mention specifically of this being the issue in the output or logs on the server.
Tags:
addr, arpa, errors, bind, solutioncentos, copying, restarting, restart, thoroughly, zones, grep, ttl, origin, soa, ns, rtt, refresh, update, retry, expiry, nx, nxdomain, ptr, testdns, dubmail, www, vlan, tehka, khyra, skulda, thehip, ccipe, tld, tolerated, versions, previous, dots, output, logs, server,